| Package | hl7.terminology |
| Type | ValueSet |
| Id | Id |
| FHIR Version | R5 |
| Source | http://terminology.hl7.org/https://build.fhir.org/ig/HL7/UTG/ValueSet-v3-RoleClass.html |
| Url | http://terminology.hl7.org/ValueSet/v3-RoleClass |
| Version | 3.0.0 |
| Status | active |
| Date | 2014-03-26 |
| Name | RoleClass |
| Title | RoleClass |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | This table includes codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role. The role hierarchy stems from three core concepts, or abstract domains: * **RoleClassOntological** is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity. * **RoleClassPartitive** collects roles in which the playing entity is in some sense a "part" of the scoping entity. * **RoleClassAssociative** collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between: * **RoleClassPassive** which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity. * **RoleClassMutualRelationship** which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may be *de facto* behavior. Thus, this sub-domain is further divided into: * **RoleClassRelationshipFormal** in which the relationship is formally defined, frequently by a contract or agreement. * **Personal relationship** which inks two people in a personal relationship. The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the "Personal relationship" which is a leaf concept. |
| Copyright | This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html |
| StructureDefinition | |
https://fhir.ee/base/StructureDefinition/ee-related-person  | EEBase RelatedPerson |
| CodeSystem | |
| v3-RoleClass | RoleClass |
Note: links and images are rebased to the (stated) source
Generated Narrative: ValueSet v3-RoleClass
Language: en
FHIRhttp://terminology.hl7.org/CodeSystem/v3-RoleClass{
"resourceType" : "ValueSet",
"id" : "v3-RoleClass",
"language" : "en",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet v3-RoleClass</b></p><a name=\"v3-RoleClass\"> </a><a name=\"hcv3-RoleClass\"> </a><a name=\"v3-RoleClass-en-US\"> </a><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Language: en</p></div><ul><li>Include all codes defined in <a href=\"CodeSystem-v3-RoleClass.html\"><code>http://terminology.hl7.org/CodeSystem/v3-RoleClass</code></a></li></ul></div>"
},
"url" : "http://terminology.hl7.org/ValueSet/v3-RoleClass",
"identifier" : [
{
"system" : "urn:ietf:rfc:3986",
"value" : "urn:oid:2.16.840.1.113883.1.11.11555"
}
],
"version" : "3.0.0",
"name" : "RoleClass",
"title" : "RoleClass",
"status" : "active",
"experimental" : false,
"date" : "2014-03-26",
"publisher" : "Health Level Seven International",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://hl7.org"
},
{
"system" : "email",
"value" : "hq@HL7.org"
}
]
}
],
"description" : "This table includes codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role.\r\n\r\nThe role hierarchy stems from three core concepts, or abstract domains:\r\n\r\n * **RoleClassOntological** is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity.\r\n * **RoleClassPartitive** collects roles in which the playing entity is in some sense a \"part\" of the scoping entity.\r\n * **RoleClassAssociative** collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between:\r\n \r\n * **RoleClassPassive** which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity.\r\n * **RoleClassMutualRelationship** which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may be *de facto* behavior. Thus, this sub-domain is further divided into:\r\n \r\n * **RoleClassRelationshipFormal** in which the relationship is formally defined, frequently by a contract or agreement.\r\n * **Personal relationship** which inks two people in a personal relationship.\r\n\r\nThe hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the \"Personal relationship\" which is a leaf concept.",
"immutable" : true,
"copyright" : "This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html",
"compose" : {
"include" : [
{
"system" : "http://terminology.hl7.org/CodeSystem/v3-RoleClass"
}
]
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.